Search for: All records

The sources of the astrophysical neutrino flux discovered by IceCube remain for the most part unresolved. Extragalactic core-collapse supernovae (CCSNe) have been suggested as potentially able to produce high-energy neutrinos. In recent years, the Zwicky Transient Facility has discovered a population of exceptionally luminous supernovae, whose powering mechanisms have not yet been fully established. A fraction of these objects fall in the broader category of type IIn CCSNe, showing signs of interaction with a dense circumstellar medium. Theoretical models connect the supernova photometric properties to the dynamics of a shock-powered emission, predicting particle acceleration. In this contribution, we outline the plan for a search of high-energy neutrinos targeting the population of superluminous and type IIn supernovae with the IceCube Neutrino Observatory. 

The Zwicky Transient Facility (ZTF) performs a systematic neutrino follow-up programme, searching for optical counterparts to high-energy neutrinos with dedicated Target-of-Opportunity (ToO) observations. Since first light in March 2018, ZTF has taken prompt observations for 24 high-quality neutrino alerts from the IceCube Neutrino Observatory, with a median latency of 12.2 h from initial neutrino detection. From two of these campaigns, we have already reported tidal disruption event (TDE) AT 2019dsg and likely TDE AT 2019fdr as probable counterparts, suggesting that TDEs contribute >7.8 per cent of the astrophysical neutrino flux. We here present the full results of our programme through to December 2021. No additional candidate neutrino sources were identified by our programme, allowing us to place the first constraints on the underlying optical luminosity function of astrophysical neutrino sources. Transients with optical absolutes magnitudes brighter that −21 can contribute no more than 87 per cent of the total, while transients brighter than −22 can contribute no more than 58 per cent of the total, neglecting the effect of extinction and assuming they follow the star formation rate. These are the first observational constraints on the neutrino emission of bright populations such as superluminous supernovae. None of the neutrinos were coincident with bright optical AGN flares comparable to that observed for TXS 0506+056/IC170922A, with such optical blazar flares producing no more than 26 per cent of the total neutrino flux. We highlight the outlook for electromagnetic neutrino follow-up programmes, including the expected potential for the Rubin Observatory.

 

Current neutrino detectors will observe hundreds to thousands of neutrinos from Galactic supernovae, and future detectors will increase this yield by an order of magnitude or more. With such a data set comes the potential for a huge increase in our understanding of the explosions of massive stars, nuclear physics under extreme conditions, and the properties of the neutrino. However, there is currently a large gap between supernova simulations and the corresponding signals in neutrino detectors, which will make any comparison between theory and observation very difficult. SNEWPY is an open-source software package that bridges this gap. The SNEWPY code can interface with supernova simulation data to generate from the model either a time series of neutrino spectral fluences at Earth, or the total time-integrated spectral fluence. Data from several hundred simulations of core-collapse, thermonuclear, and pair-instability supernovae is included in the package. This output may then be used by an event generator such as sntools or an event rate calculator such as the SuperNova Observatories with General Long Baseline Experiment Simulator (SNOwGLoBES). Additional routines in the SNEWPY package automate the processing of the generated data through the SNOwGLoBES software and collate its output into the observable channels of each detector. In this paper we describe the contents of the package, the physics behind SNEWPY, the organization of the code, and provide examples of how to make use of its capabilities.

 

Developing sustainable software for the scientific community requires expertise in software engineering and domain science. This can be challenging due to the unique needs of scientific software, the insufficient resources for software engineering practices in the scientific community, and the complexity of developing for evolving scientific contexts. While open‐source software can partially address these concerns, it can introduce complicating dependencies and delay development. These issues can be reduced if scientists and software developers collaborate. We present a case study wherein scientists from the SuperNova Early Warning System collaborated with software developers from the Scalable Cyberinfrastructure for Multi‐Messenger Astrophysics project. The collaboration addressed the difficulties of open‐source software development, but presented additional risks to each team. For the scientists, there was a concern of relying on external systems and lacking control in the development process. For the developers, there was a risk in supporting a user‐group while maintaining core development. These issues were mitigated by creating a second Agile Scrum framework in parallel with the developers' ongoing Agile Scrum process. This Agile collaboration promoted communication, ensured that the scientists had an active role in development, and allowed the developers to evaluate and implement the scientists' software requirements. The collaboration provided benefits for each group: the scientists actuated their development by using an existing platform, and the developers utilized the scientists' use‐case to improve their systems. This case study suggests that scientists and software developers can avoid scientific computing issues by collaborating and that Agile Scrum methods can address emergent concerns.